home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Libris Britannia 4
/
science library(b).zip
/
science library(b)
/
INFO
/
PCCDEMO.ZIP
/
COMP1.EXE
/
DBLSPACE.PRS
< prev
next >
Wrap
Text File
|
1993-12-20
|
6KB
|
100 lines
âüïÆÅÇéä ÆÄïöôêÄìÆ ╬╠╬╠╬╠╬╠╬╠╧╧╬╠╬╠╡
│ α ≥εδ⌠≤Φεφ ≤ε α πßδ≥∩αΓΣ ∩±εßδΣ∞
│
πßδ≥∩αΓΣ Γ±α≥τΦφµ ≥εδ⌠≤Φεφ │ ß√ ≥Φµ⌠±π µδαΣ±⌠∞
│
Σ≈∩αφπΦφµ πßδ≥∩αΓΣ │ I am one of the multitude (it
│ seems) of people who have
│ experienced serious problems with
││ │ │ DOS 6 and Dblspace.
┌─┤├─┐ │┌─┐┌─┐┌─┐┌─┐┌─┐ │ Lots of files got mysteriously
│ ││ │ │└─┐│ │┌─┤│ ├─┘ │ lost, even whole directories went
└─┘└─┘ ┴└─┘├─┘└─┘└─┘└─┘ │ missing.
│ │ Well, I'm not easily scared
│ │ ≥Φµ⌠±π µδαΣ±⌠∞ │ off so I plodded on, trying every
├─┐┌─┐ │┌─┐ and │ conceivable method to find the
│ │├─┘ ││ │ ≤Φαφµ σεε │ reason for this strange behavior.
└ └└─┘ ┴├─┘ │ Nothing turned up and matters
│ │ just got worse: after a few days
│ DOS reported a damaged CVF and
│ the next day the machine didn't
│ recognize the hard disk at all!
│ drive is somewhat incompatible
Okay, I thought, desperate │ with DOS 6 setup (or FORMAT).
measures are in order. I │ The solution was to partition
partitioned and formatted my │ and format with DOS 5 THEN do a
hard disk and tried to install │ manual install of DOS 6. It
DOS 6 anew. It didn't work. │ works like a dream now (touch
Setup created chaos on my hard │ wood).
disk. Tried manual install, but │
transferring the system from a │ Moral: if you experience
boot diskette with "sys c:" also │ unexplainable behavior, call
made mush of the hard disk! │ Microsoft and have them check
Chkdsk reported a "probable non- │ your disk-drive etc. against
DOS disk" and Norton Disk Doctor │ their list of incompatible
"media descriptor byte invalid". │ hardware.
Note that this was before I tried │
installing Dblspace. │
│ πßδ≥∩αΓΣ Σ≈α∩φπ
Well, after numerous calls to │
Microsoft the reason finally │ ß√ ≤Φαφµ σεε
emerged, my Microscience IDE │
When you use dblspace in Dos │ your RAM is not enough(4 MB).
6.0, it will compress your C: │
drive and create a H:(or │ Anyway, if for some reason you
host_of_C) drive as a working │ need to increase to work space in
drive. By default the size of H: │ H: drive, you will have to use
drive is 2 MB so to maximize the │ the command <dblspace /size
size of compressed drive C:. │ /reserve=??>.
Unfortunately, some programs │ This command will also
(softwares) require a larger work │ decrease the size of your
space (on H: drive) than the │ compressed drice C:. No suprise.
default size of 2 MB. Example, │ The problem was that the above
the default swap space for │ command will do no good without
MATLAB(using cfig386.exe memory │ some tricks. When you use the
extender) is 10 MB. Even though │ above command, you will see a
MATLAB will run with 2MB, it will │ system message saying "your drive
spend more time swapping than │ is too fragmented, cannot
doing the actual work when you │ resize". It also suggests you
are manipulating huge arrays │ run another command <defrag /q /h
(matrices). I think Windows also │ C:> before you resize. You can do
requires larger swap space if │ help in DOS to see what DEFRAG
does. Basically, it will │ work correctly.
optimize the disk. It is a long │
process - might take up to two │ Here is what you can try.
hours. To everyone's │
disappointment, the two hours' │ c:\ attrib -s -h -r *.*
wait doesn't do you any good. │ /* I think above step is the
You will receive the same message │ crucial part */
when you try <dblspace...> again. │ c:\ defrag /q /h c:
│ /* message on screen
Dblspace keeps all the disk │ ..optimizing.. defragmetation..*/
info in a single file name │ c:\ dblspace /size /reserve=20
<dblspace.ini>. This is a hidden │ /* It works!!!!!!!!!!!!!!!!!!!*/
file. You have to change its │
attribute to an ordinary file so │
that the DEFRAG treat this file │ Remember to record the files
as any regular file when it is │ with special attribute before you
defragmenting the drive. Or else │ try <attrib -h -r -s *.*>. Use
<defrag /q /h C:> is no good. │ <dir /a> to see all file's
So, after the defragmentation, │ attributes. Also, remember to set
<dblspace /size /reserve=??> will │ the special files back to their
initial attribute after resize │
with < attrib [+h | +r | +s] │
filename > command. │
│
Make sure that what you have │
on your HD is backed up, you are │
running a risk of looding the │
file, however, it should work │
fine. Do it on your own risk tho!ñ │